…1371)

…sing JDK >= 9 for Maven

…1191)

Version `4.6.1` of previously used artifact `org.eclipse.jdt:ecj`
was actually version of Eclipse IDE.

This version supports source/target from Java 1.1 up to 19.

Also note that starting from version `3.27.0` ECJ requires Java 11
for execution.

…4.27 (jacoco#1414)

This allows format checking of the integration test targets up to Java 20.

…plication class loader (jacoco#1334)

Co-authored-by: Evgeny Mandrikov <mandrikov@gmail.com>
Co-authored-by: Marc R. Hoffmann <hoffmann@mountainminds.com>

…#1425)

Update branch with master

…acoco#1454)

This change fixes flaws of
4dc8b38
and
740c51f
i.e. `build.commitId` is correctly computed
and tests can be executed in IntelliJ IDEA.

Quoting https://openjdk.org/jeps/440

> Apart from some minor editorial changes, the main change since the
> second preview is to remove support for record patterns appearing in
> the header of an enhanced for statement.

It requires Maven 3.5.4 and thus transitively our build should require it too.

…co#1468)

Note that `org.apache.maven.shared:file-management` version `3.1.0`
requires Java 8.

Record patterns and pattern matching for switch are finalized in Java 21,
so no need to test them as preview features in earlier versions.

…acoco#1476)

* Nowadays AppVeyor sets `M2_HOME` pointing on preinstalled Maven,
  so the execution of downloaded `apache-maven-3.3.9\bin\mvn`
  actually leads to the execution of preinstalled.

* Also `mvn` uses `JAVA_HOME`, so its addition to `PATH` is
  not needed.

It requires Java 17 and thus transitively our build should require it too.

…37.0 (jacoco#1493)

Merge upstream master